AssetWise System Management Console Help

Configuring AssetWise Services

A default installation of AssetWise Server installs the AssetWise Information Integrity Server as well as many additional AssetWise services. Also, other AssetWise server installations that rely on these additional services deliver and install the necessary services if they are not already installed on that computer. Wherever AssetWise services are installed, AssetWise System Management Console will also be installed, and is where all AssetWise services on that computer are configured and managed.

In AssetWise System Management Console, the Service Manager node is used to manage the services installed on a particular computer. From here you can see the status of each service, stop and start services individually or all at once, and edit service properties including the ports used by each service. See Using Service Manager for details.

There is also a dedicated node in AssetWise System Management Console where you can configure each service that is installed:

  • Storage Service - Storage node
  • Rendition Service - Rendition node
  • Print Service - Print node
  • FTR Service - FTR node
  • Mail Distribution Service - Mail Distribution node
  • Publishing Service - Publisher node
  • Snapshot Capture Service - Snapshot Capture node
  • Document Creation Service - Document Creation node
  • Interoperability Service - Interoperability node
  • Work Queue Service - Work Queue node
  • ProjectWise Connector Service – Sync node (when ProjectWise connector is installed)

When you select one of these nodes, the content pane displays a list of available communities in the Communities Served list. Next to each community is a check box. If you want a community to use a particular service, select the node for the service, check the check box next to your community, and log in if prompted. That service running on that server is now enabled to serve the selected community. To disable a service from serving a community, uncheck the check box.

For some services, the only configuration required is to enable the service for the community. Other services require additional configuration.

Work that comes into AssetWise for either the Storage Service or the Rendition Service comes in the form of a job. As jobs come into AssetWise they are grouped by function and written to a job queue. Agents for each media service monitor and service these job queues. Monitoring these queues is discussed in the section, Monitoring Job Queues in Your Community .

Note: Some AssetWise services have individual engines associated with them. When you enable one of these services for a community, the individual engines are (usually) automatically added to the Engines node within the community. See Adding Custom Engines to the Community .